NO-JIRA: Update hello-openshift base images from 4.16/4.17 to 4.22#31264
Conversation
The builder and base images referenced ocp/4.16 and 4.17 which have been pruned from the CI registry, causing PullBuilderImageFailed on all payload-job-with-prs runs. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
Pipeline controller notification For optional jobs, comment This repository is configured in: automatic mode |
WalkthroughThe hello-openshift Dockerfile base images are updated to OpenShift 4.22 with Go 1.25, replacing the previous 4.17/Go 1.22 builder and 4.16 runtime base images. Build steps and runtime instructions remain unchanged. ChangesBase Image Version Bump
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes 🚥 Pre-merge checks | ✅ 14 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (14 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
@sdodson Is that something you could help reviewing? |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
images/hello-openshift/Dockerfile.rhel (1)
1-11: 🛠️ Refactor suggestion | 🟠 Major | ⚡ Quick winAdd HEALTHCHECK instruction.
The Dockerfile is missing a
HEALTHCHECKinstruction, which is required by the coding guidelines. Since the application exposes ports 8080 and 8888, consider adding a health check to verify the service is responding.🏥 Proposed addition of HEALTHCHECK
FROM registry.ci.openshift.org/ocp/4.22:base-rhel9 COPY --from=builder /hello-openshift /hello-openshift EXPOSE 8080 8888 +HEALTHCHECK --interval=30s --timeout=3s --start-period=5s --retries=3 \ + CMD ["/usr/bin/curl", "-f", "http://localhost:8080/", "||", "exit", "1"] USER 1001 ENTRYPOINT ["/hello-openshift"]Note: Verify that
curlis available in the base image, or use an alternative health check method appropriate for the hello-openshift application.As per coding guidelines, the container security (prodsec-skills) section requires: "HEALTHCHECK defined".
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@images/hello-openshift/Dockerfile.rhel` around lines 1 - 11, Add a HEALTHCHECK instruction to the Dockerfile to satisfy the "HEALTHCHECK defined" guideline: add a HEALTHCHECK that calls the running binary (ENTRYPOINT /hello-openshift) over an exposed port (e.g., HTTP GET to :8080 or :8888) and returns non-zero on failure; ensure the command uses binaries available in the base image (curl/wget or an exec-style check) and set sensible --interval/--timeout/--retries values so the container health reflects the application responsiveness.Source: Coding guidelines
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@images/hello-openshift/Dockerfile.rhel`:
- Line 1: Add a HEALTHCHECK instruction to
images/hello-openshift/Dockerfile.rhel to satisfy container security guidelines
(e.g., a minimal CMD that probes the app or exits appropriately) and ensure it
uses sensible intervals/retries; also review the two FROM lines (the builder
stage "FROM
registry.ci.openshift.org/ocp/builder:rhel-9-golang-1.25-openshift-4.22" and the
runtime stage that also references registry.ci.openshift.org) and either change
them to the approved catalog.redhat.com equivalents or document/confirm the
OpenShift CI exception for using registry.ci.openshift.org with the
release/maintainers so the base image registry usage is intentional.
---
Outside diff comments:
In `@images/hello-openshift/Dockerfile.rhel`:
- Around line 1-11: Add a HEALTHCHECK instruction to the Dockerfile to satisfy
the "HEALTHCHECK defined" guideline: add a HEALTHCHECK that calls the running
binary (ENTRYPOINT /hello-openshift) over an exposed port (e.g., HTTP GET to
:8080 or :8888) and returns non-zero on failure; ensure the command uses
binaries available in the base image (curl/wget or an exec-style check) and set
sensible --interval/--timeout/--retries values so the container health reflects
the application responsiveness.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository YAML (base), Central YAML (inherited)
Review profile: CHILL
Plan: Enterprise
Run ID: 53384846-3916-459b-95b4-d41255985737
📒 Files selected for processing (1)
images/hello-openshift/Dockerfile.rhel
|
@anuragthehatter: This PR was included in a payload test run from openshift/cluster-network-operator#3015
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/30323330-6145-11f1-8085-18a113a858ae-0 |
|
Scheduling required tests: |
|
@anuragthehatter: This PR was included in a payload test run from openshift/cluster-network-operator#3015
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/a0e017d0-6345-11f1-9c80-ac8ee1ba40aa-0 |
|
Seems job passing now https://pr-payload-tests.ci.openshift.org/runs/ci/30323330-6145-11f1-8085-18a113a858ae-0 |
openshift-ci
Bot
added
the
ready-for-human-review
|
/pj-rehearse ack |
|
/lgtm |
openshift-ci
Bot
changed the title
openshift-ci-robot
added
the
jira/valid-reference
|
@anuragthehatter: This pull request explicitly references no jira issue. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
openshift-ci-robot
added
the
verified
|
@sdodson: This PR has been marked as verified by DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: anuragthehatter, sdodson The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openshift-ci
Bot
added
the
approved
|
@anuragthehatter: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
3 participants
Summary
images/hello-openshift/Dockerfile.rhelfrom ocp/4.16 and 4.17 to 4.22PullBuilderImageFailedon payload-job-with-prs runsTest plan
🤖 Generated with Claude Code
Summary by CodeRabbit